Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change to use PAT auth for GitLab #2689

Merged
merged 1 commit into from
Feb 1, 2021
Merged

Change to use PAT auth for GitLab #2689

merged 1 commit into from
Feb 1, 2021

Conversation

bwateratmsft
Copy link
Contributor

Fixes #1968 (and #2688). Using OAuth for GitLab is no longer feasible since it requires the user to register a client application and provide that app ID and secret in addition to username and password. Personal access token auth is the only realistic option at this point.

@bwateratmsft bwateratmsft requested a review from a team as a code owner February 1, 2021 16:23
@bwateratmsft bwateratmsft merged commit 46ddddd into main Feb 1, 2021
@bwateratmsft bwateratmsft deleted the bmw/gitLabPat branch February 1, 2021 16:49
@bwateratmsft bwateratmsft linked an issue Feb 1, 2021 that may be closed by this pull request
Dmarch28 pushed a commit to Dmarch28/vscode-docker that referenced this pull request Mar 4, 2021
@microsoft microsoft locked and limited conversation to collaborators Oct 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gitlab registry oauth (unknown client) Cannot use personal access token to connect to GitLab
2 participants